fix: reset frame when read to EOF to release buffer in Block #220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We use reader to decompress with no pooling object, it's some code like:
and we found a big performace regression when we upgrade to v4.1.21 (from v4.0.2), after some test we narrow down the change from v4.1.0 -> v4.1.1.
It's seems that the code do
BlockSizeIndex.Get()
twice and only callPut()
to return the buffer 1 time. It look like that the buffer from this stack is not released.So here i added a Reset when read to EOF, to release the underlying buffer in
Block
.Added a Benchmark test: